This PR implements automatic VERSION file updates with GitVersion semver on each checkout, allowing developers to easily see what version they're currently working on.

Changes Made

1. Created VERSION File

• Added a VERSION file in the repository root that gets automatically updated
• Initially set to 1.0.0 and managed by the version update system

2. Version Update Script

Created update-version.sh that intelligently determines the current version:

# Tries GitVersion first for proper semver calculation
dotnet-gitversion -config .gitversion -showvariable MajorMinorPatch

# Falls back to git describe when GitVersion returns defaults
git describe --tags --always --dirty

The script handles various scenarios:

• GitVersion available: Uses calculated semver from GitVersion configuration
• GitVersion returns default (1.0.0): Falls back to extracting version from git tags
• Git describe: Extracts meaningful version from tag patterns like feature_larasets_5.10.2 → 5.10.2-2-g51926a7
• Error handling: Maintains existing VERSION file if no version can be determined

3. Enhanced Post-Checkout Hook

Modified src/githooks/_post-checkout.sh to automatically call the version update script:

# Update VERSION file with current GitVersion semver
if [ -f "./update-version.sh" ]; then
  ./update-version.sh || zz_log w "Failed to update VERSION file"
else
  zz_log w "update-version.sh script not found, skipping VERSION file update"
fi

How It Works

1. On Checkout: The post-checkout hook runs automatically when switching branches/commits
2. Version Detection: The script determines the current version using GitVersion or git describe fallback
3. File Update: The VERSION file is updated with the detected semver
4. Developer Visibility: Developers can run cat VERSION to see their current working version

Example Usage

# After checking out any branch
$ cat VERSION
5.10.2-3-g51926a7

# The file automatically updates on checkout
$ git checkout main
$ cat VERSION
5.10.3-1-g8a2b3c4

This integrates seamlessly with the existing GitVersion configuration and devcontainer features workflow, requiring no manual intervention once the githooks feature is installed and configured.

Fixes #10.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.